Skip to content

Conversation

@leonerd
Copy link
Contributor

@leonerd leonerd commented Jan 8, 2026

OP_MULTIPARAM now handles all of the processing for subroutine signatures. It is useful to show a summary of its contents in the output of B::Deparse.

The output is now, for example:

2           <+> multiparam(2 $x,$y) ->3

to indicate two mandatory parameters being stored into $x and $y, where before it would have been simply

2           <+> multiparam() ->3

Fixes #24064

`OP_MULTIPARAM` now handles all of the processing for subroutine
signatures. It is useful to show a summary of its contents in the output
of `B::Deparse`.

The output is now, for example:

  2           <+> multiparam(2 $x,$y) ->3

to indicate two mandatory parameters being stored into `$x` and `$y`,
where before it would have been simply

  2           <+> multiparam() ->3

Fixes Perl#24064
@leonerd leonerd requested a review from tonycoz January 8, 2026 19:34
@leonerd leonerd merged commit 09c977d into Perl:blead Jan 11, 2026
34 checks passed
@leonerd leonerd deleted the gh24064 branch January 11, 2026 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

B::UNOP_AUX::string doesn't handle new multiparam op

2 participants